Pre-bundles the vitest runtime for browser mode so the browser fetches a few optimized chunks instead of ~20 separately-served dist chunks (faster startup, fewer module requests).

vitest, vitest/internal/browser and @vitest/browser/client are moved from optimizeDeps.exclude to include. They are optimized together in a single pass, so esbuild dedupes their shared stateful chunks (the test collector, the runner, the RPC client) to a single instance — preserving module identity between the test files' import 'vitest' and the tester. Their transitive deps (@vitest/utils, @vitest/spy, pathe, tinyrainbow, …) are inlined into these bundles. The virtual per-server modules (@vitest/browser/context, …), vite/module-runner and msw must stay excluded (see the comment in index.ts).

Shared-server resolver fix. The vitest:resolve-core plugin (vitestResolver.ts) short-circuits bare vitest imports straight to the running copy's dist file. It now lives on the single Vite server shared by every environment, so it also governs the browser client environment where the runtime is pre-bundled — without care the tester would use the optimized bundle while test files receive the raw dist graph, producing two @vitest/runner instances and failing every test() with "Vitest failed to find the current suite". When the environment includes vitest in optimizeDeps, the plugin now routes the import through the optimizer (this.resolve) so both share one instance; every other environment keeps the pinned dist resolution.

Stack frames pointing into the optimizer cache (.vite/vitest) are ignored in stack traces like the un-bundled /vitest/dist/ ones. The console-logging spec now runs with an explicit default reporter and asserts on Vitest's own console forwarding: once the runtime is pre-bundled the tester loads a stubbed @vite/client, so Vite's client console relay no longer runs.